<meta charset="utf-8">
(#) Use getViewLifecycleOwner() as the LifecycleOwner instead of a Fragment instance when observing a LiveData object

!!! ERROR: Use getViewLifecycleOwner() as the LifecycleOwner instead of a Fragment instance when observing a LiveData object
   This is an error.

Id
:   `FragmentLiveDataObserve`
Summary
:   Use getViewLifecycleOwner() as the LifecycleOwner instead of a Fragment instance when observing a LiveData object
Severity
:   Error
Category
:   Correctness
Platform
:   Android
Vendor
:   Android Open Source Project
Identifier
:   androidx.fragment
Feedback
:   https://issuetracker.google.com/issues/new?component=460964
Min
:   Lint 7.0
Compiled
:   Lint 8.0 and 8.1
Artifact
:   [androidx.fragment:fragment](androidx_fragment_fragment.md.html)
Since
:   1.2.0
Affects
:   Kotlin and Java files
Editing
:   This check runs on the fly in the IDE editor
Implementation
:   [Source Code](https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:/fragment/fragment-lint/src/main/java/androidx/fragment/lint/UnsafeFragmentLifecycleObserverDetector.kt)
Tests
:   [Source Code](https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:/fragment/fragment-lint/src/test/java/androidx/fragment/lint/FragmentLiveDataObserveDetectorTest.kt)
Copyright Year
:   2019

When observing a LiveData object from a fragment's onCreateView,
        onViewCreated, onActivityCreated, or onViewStateRestored method
               getViewLifecycleOwner() should be used as the
LifecycleOwner rather than the                 Fragment instance. The
Fragment lifecycle can result in the Fragment being
active longer than its view. This can lead to unexpected behavior from
              LiveData objects being observed longer than the Fragment's
view is active.

(##) Including

!!!
   This is not a built-in check. To include it, add the below dependency
   to your project.

```
// build.gradle.kts
implementation("androidx.fragment:fragment:1.8.5")

// build.gradle
implementation 'androidx.fragment:fragment:1.8.5'

// build.gradle.kts with version catalogs:
implementation(libs.fragment)

# libs.versions.toml
[versions]
fragment = "1.8.5"
[libraries]
# For clarity and text wrapping purposes the following declaration is
# shown split up across lines, but in TOML it needs to be on a single
# line (see https://github.com/toml-lang/toml/issues/516) so adjust
# when pasting into libs.versions.toml:
fragment = {
    module = "androidx.fragment:fragment",
    version.ref = "fragment"
}
```

1.8.5 is the version this documentation was generated from;
there may be newer versions available.

[Additional details about androidx.fragment:fragment](androidx_fragment_fragment.md.html).
(##) Suppressing

You can suppress false positives using one of the following mechanisms:

* Using a suppression annotation like this on the enclosing
  element:

  ```kt
  // Kotlin
  @Suppress("FragmentLiveDataObserve")
  fun method() {
     problematicStatement()
  }
  ```

  or

  ```java
  // Java
  @SuppressWarnings("FragmentLiveDataObserve")
  void method() {
     problematicStatement();
  }
  ```

* Using a suppression comment like this on the line above:

  ```kt
  //noinspection FragmentLiveDataObserve
  problematicStatement()
  ```

* Using a special `lint.xml` file in the source tree which turns off
  the check in that folder and any sub folder. A simple file might look
  like this:
  ```xml
  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
  &lt;lint&gt;
      &lt;issue id="FragmentLiveDataObserve" severity="ignore" /&gt;
  &lt;/lint&gt;
  ```
  Instead of `ignore` you can also change the severity here, for
  example from `error` to `warning`. You can find additional
  documentation on how to filter issues by path, regular expression and
  so on
  [here](https://googlesamples.github.io/android-custom-lint-rules/usage/lintxml.md.html).

* In Gradle projects, using the DSL syntax to configure lint. For
  example, you can use something like
  ```gradle
  lintOptions {
      disable 'FragmentLiveDataObserve'
  }
  ```
  In Android projects this should be nested inside an `android { }`
  block.

* For manual invocations of `lint`, using the `--ignore` flag:
  ```
  $ lint --ignore FragmentLiveDataObserve ...`
  ```

* Last, but not least, using baselines, as discussed
  [here](https://googlesamples.github.io/android-custom-lint-rules/usage/baselines.md.html).

<!-- Markdeep: --><style class="fallback">body{visibility:hidden;white-space:pre;font-family:monospace}</style><script src="markdeep.min.js" charset="utf-8"></script><script src="https://morgan3d.github.io/markdeep/latest/markdeep.min.js" charset="utf-8"></script><script>window.alreadyProcessedMarkdeep||(document.body.style.visibility="visible")</script>